@DDvO Hi, would it not be better to think about some sort of RAT-Provider, which allow some easier integration, of atg or some TPM2 logic, so just let the nonce and some optional parameters parsed to it. Which is parsed, base on some provider key=value options.

@DDvO Hi, would it not be better to think about some sort of RAT-Provider,

I am not sure if I fully understood what you mean,
but please note that this addition to support remote attestation is not something that can be seen as an OpenSSL crypto provider. The provider API only covers basic crypto(-related) functionality such as signing, encryption and/or random number generation.

BTW, @rajeev-0 who takes care of the review comments I gave here and in #121?

In particular, to avoid needless clutter at many unrelated places,
the code should not introduce its own CMP_RAT_CTX - this is simply not needed.

@DDvO Hi, would it not be better to think about some sort of RAT-Provider,

I am not sure if I fully understood what you mean, but please note that this addition to support remote attestation is not something that can be seen as an OpenSSL crypto provider. The provider API only covers basic crypto(-related) functionality such as signing, encryption and/or random number generation.

I was thinking about some new mechanism, to add different remote attestation logic in a shared interface, and Provider, was just a temporary name. And since you have a lot of experience with OpenSSL, I was curious about your ideas or solutions to add such a new feature.